CentOS 7
Sponsored Link

OpenStack Liberty : Use Cinder Storage(GlusterFS)
2015/11/17
 
It's possible to use the Virtual Storage provided by Cinder if an Instance needs more disks.
Configure Virtual storage with GlusterFS backend on here.
                                      +------------------+           +------------------+
                             10.0.0.50| [ Storage Node ] |  10.0.0.61|                  |
+------------------+            +-----+   Cinder-Volume  |     +-----+   GlusterFS #1   |
| [ Control Node ] |            | eth0|                  |     | eth0|                  |
|     Keystone     |10.0.0.30   |     +------------------+     |     +------------------+
|      Glance      |------------+------------------------------+
|     Nova API     |eth0        |     +------------------+     |     +------------------+
|    Cinder API    |            | eth0| [ Compute Node ] |     | eth0|                  |
+------------------+            +-----+   Nova Compute   |     +-----+   GlusterFS #2   |
                             10.0.0.51|                  |  10.0.0.62|                  |
                                      +------------------+           +------------------+

[1]
GlusterFS server is required to be running on your LAN, refer to here.
This example uses a replication volume "vol_replica" provided by "gfs01" and "gfs02".
[2] Configure Storage Node.
# install from EPEL

[root@storage ~]#
yum --enablerepo=epel -y install glusterfs glusterfs-fuse
[root@storage ~]#
vi /etc/cinder/cinder.conf
# add follows in the [DEFAULT] section

enabled_backends = glusterfs
# add follwos to the end

[glusterfs]
volume_driver = cinder.volume.drivers.glusterfs.GlusterfsDriver
glusterfs_shares_config = /etc/cinder/glusterfs_shares
glusterfs_mount_point_base = $state_path/mnt_gluster
[root@storage ~]#
vi /etc/cinder/glusterfs_shares
# create new : specify GlusterFS volumes

gfs01.srv.world:/vol_replica
[root@storage ~]#
chmod 640 /etc/cinder/glusterfs_shares

[root@storage ~]#
chgrp cinder /etc/cinder/glusterfs_shares

[root@storage ~]#
systemctl restart openstack-cinder-volume

[3] Configure Compute Node to mount GlusterFS volume.
# install from EPEL

[root@node01 ~]#
yum --enablerepo=epel -y install glusterfs glusterfs-fuse
[root@node01 ~]#
vi /etc/nova/nova.conf
# add follows in the [DEFAULT] section

osapi_volume_listen=0.0.0.0
volume_api_class=nova.volume.cinder.API
[root@node01 ~]#
systemctl restart openstack-nova-compute

[4] For example, create a virtual disk "disk01" with 10GB. It's OK to work on any node. (This example is on Control Node)
# set environment variable first

[root@dlp ~(keystone)]#
echo "export OS_VOLUME_API_VERSION=2" >> ~/keystonerc

[root@dlp ~(keystone)]#
source ~/keystonerc
[root@dlp ~(keystone)]#
cinder create --display_name disk01 10

+---------------------------------------+--------------------------------------+
|                Property               |                Value                 |
+---------------------------------------+--------------------------------------+
|              attachments              |                  []                  |
|           availability_zone           |                 nova                 |
|                bootable               |                false                 |
|          consistencygroup_id          |                 None                 |
|               created_at              |      2015-11-18T12:18:46.000000      |
|              description              |                 None                 |
|               encrypted               |                False                 |
|                   id                  | 67b2e967-f387-4a25-99ff-899608d43c83 |
|                metadata               |                  {}                  |
|            migration_status           |                 None                 |
|              multiattach              |                False                 |
|                  name                 |                disk01                |
|         os-vol-host-attr:host         |                 None                 |
|     os-vol-mig-status-attr:migstat    |                 None                 |
|     os-vol-mig-status-attr:name_id    |                 None                 |
|      os-vol-tenant-attr:tenant_id     |   d625e02b3d394afbad250def2f88fefa   |
|   os-volume-replication:driver_data   |                 None                 |
| os-volume-replication:extended_status |                 None                 |
|           replication_status          |               disabled               |
|                  size                 |                  10                  |
|              snapshot_id              |                 None                 |
|              source_volid             |                 None                 |
|                 status                |               creating               |
|                user_id                |   b4c316b93a464f8ea46b01bd01a52003   |
|              volume_type              |                 None                 |
+---------------------------------------+--------------------------------------+

[root@dlp ~(keystone)]#
cinder list

+-----------+-----------+------------------+--------+------+-------------+----------+-------------+-------------+
| ID        |   Status  | Migration Status |  Name  | Size | Volume Type | Bootable | Multiattach | Attached to |
+-----------+-----------+------------------+--------+------+-------------+----------+-------------+-------------+
| 67b2e967- | available |        -         | disk01 |  10  |      -      |  false   |    False    |             |
+-----------+-----------+------------------+--------+------+-------------+----------+-------------+-------------+
[5] Attach the virtual disk to an Instance.
For the exmaple below, the disk is connected as "/dev/vdb". It's possible to use it as a storage to create a file system on it.
[root@dlp ~(keystone)]#
nova list

+-----------+----------+---------+------------+-------------+-----------------------+
| ID        | Name     | Status  | Task State | Power State | Networks              |
+-----------+----------+---------+------------+-------------+-----------------------+
| 74a217fa- | CentOS_7 | SHUTOFF | -          | Shutdown    | sharednet1=10.0.0.202 |
+-----------+----------+---------+------------+-------------+-----------------------+

[root@dlp ~(keystone)]#
nova volume-attach CentOS_7 a74a1732-0ef3-46dd-84fb-3fe62e908ec2 auto

+----------+--------------------------------------+
| Property | Value                                |
+----------+--------------------------------------+
| device   | /dev/vdb                             |
| id       | 67b2e967-f387-4a25-99ff-899608d43c83 |
| serverId | 74a217fa-4e64-4b40-90c7-8df929a2e53c |
| volumeId | 67b2e967-f387-4a25-99ff-899608d43c83 |
+----------+--------------------------------------+

# the status of attached disk turns "in-use" like follows

[root@dlp ~(keystone)]#
cinder list

+-----------+--------+------------------+--------+------+-------------+----------+-------------+----------------+
| ID        | Status | Migration Status |  Name  | Size | Volume Type | Bootable | Multiattach | Attached to    |
+-----------+--------+------------------+--------+------+-------------+----------+-------------+----------------+
| 67b2e967- | in-use |        -         | disk01 |  10  |      -      |  false   |    False    | 74a217fa-4e64- |
+-----------+--------+------------------+--------+------+-------------+----------+-------------+----------------+
 
Tweet